Please check now I updated the PR

Thanks, that's a thorough est of tests 😎

One idea: how about changing the parseAndEval approach to the following:

function parseAndStringify(expr) {
  return math.parse(expr).toString({parenthesis: 'all'})
}

// ...
assert.strictEqual(parseAndStringify('10 % 3 * 2'), '(10 % 3) * 2')

Then there is no need for the explanatory comments like // Expected as (10 % 3) * 2 = 1 * 2 = 2? We would lose checking the actual outcome though. What do you think? (I'm ok with both, it's just an idea)

Thinking about it, we could do something like this:

function assertParseAndEval(expr, expectedString, expectedResult) {
  const node = parse(expr)
  assert.strictEqual(node.toString({ parenthesis: 'all' }), expectedStr)
  approxEqual(node.evaluate(), expectedResult)
}

// ...

assertParseAndEval('10 % 3 * 2', '(10 % 3) * 2', 2)

😎

EDIT: I see there is already a helper function parseAndStringifyWithParens that is use to test implicit multiplication.

should I have to use parseAndStringifyWithParens or not ?

I'm ok with any of the three options: leave as is, create and use assertParseAndEval, or use parseAndStringifyWithParens. I have a slight preference for using parseAndStringifyWithParens. What do you think?

Ok I am going with this parseAndStringifyWithParens.I think it will be better.

done

Thanks for the quick updates 👌, merging your PR now in the v14 branch.

Published now in v14.0.0, thanks again Neeraj!